The Cisco ASA must be configured to produce audit log records containing sufficient information to establish what type of event occurred.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-239905	CASA-ND-000260	SV-239905r879563_rule		Medium

Description
It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done in order to compile an accurate risk assessment. Associating event types with detected events in the application and audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured network device. Without this capability, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.

Description

It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done in order to compile an accurate risk assessment. Associating event types with detected events in the application and audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured network device. Without this capability, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.

STIG	Date
Cisco ASA NDM Security Technical Implementation Guide	2023-05-02

Details

Check Text ( C-43138r666076_chk )
Review the Cisco ASA configuration to verify that it is compliant with this requirement. The configuration should look similar to the example below: logging enable logging buffered informational If the ASA is not configured to generate audit records containing information to establish what type of event occurred, this is a finding.

Fix Text (F-43097r666077_fix)
Configure the Cisco ASA as shown in the example below. ASA(config)# logging enable ASA(config)# logging buffered informational ASA(config)# end